Implement Event Router RFC vertical slice from issue #8287 - #2
Draft
ritofactory-dev[bot] wants to merge 1 commit into
Draft
Implement Event Router RFC vertical slice from issue #8287#2ritofactory-dev[bot] wants to merge 1 commit into
ritofactory-dev[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Experimental fork-only implementation
Warning
This is an authorized RitoFactory experiment for the RFC in aws-powertools#8287. It is incomplete, its API may change, and it must not be submitted to or represented as approved by the upstream project.
This draft implements one bounded vertical slice: a reusable exact-match router core plus
EventBridgeRouter, typedEventBridgeEventdispatch, explicit shape/no-match errors, focused tests, documentation, and an example.Deferred RFC scope
Verification evidence
Builder MicroVM reported:
python -m ruff format aws_lambda_powertools/event_router tests/unit/event_router examples/event_router --check- passedpython -m ruff check aws_lambda_powertools/event_router tests/unit/event_router examples/event_router- passedpython -m mypy --pretty aws_lambda_powertools/event_router examples/event_router- passed after installing missing boto3 stubspython -m ty check aws_lambda_powertools/event_router- passedpython -m pytest tests/unit/event_router -v --cov=aws_lambda_powertools/event_router --cov-report=term-missing- 12 passed, 96.12% module coveragepython -m compileall -q aws_lambda_powertools/event_router tests/unit/event_router examples/event_router- passedgit diff --check- passedLimitations: full
make pr, documentation build/lint, security and complexity baselines, and the full repository suite were not run. The Reviewer MicroVM lacked pytest/ruff/mypy/ty, so it reproduced behavior manually but could not independently reproduce the reported tool output. No GitHub checks are currently registered on this fork.RitoFactory provenance
run_156c99ed242229fde9a6c112d128e6f2wki_73f39c146508486354166a3789c60b99pwf_d54e8a7e2af9548d27283f50f6100dabversion 1ritofactory/powertools-lambda-python:developThe Reviewer returned a conditional rejection because the PR did not yet exist during review and its environment could not reproduce the builder tooling. Delivery subsequently created this draft PR; independent CI verification remains outstanding.